|
|
|
|
|
|
|
A small development team may have a version control server for several clients. Keep in mind that not all projects should use only one version control server. Larger, more complex projects may require multiple version control servers, one server per subsystem. Why such a configuration? Because development projects that design and implement applications with more than one major subsystem or component require a parallel development effort. Parallel development gives developers the flexibility of having an individual, encapsulated workspace in which to develop the subsystem. |
|
|
|
|
|
|
|
|
No two subsystems or components will be developed equally by their respective owners. Some subsystems will be more complex than others, or one owner may be a bit slower than another. It would be a mistake to force the faster subsystem team to wait for the other. With a version control strategy that supports parallel development, teams that depend on another team's subsystem or component can work with a mocked-up facade until the first stable version of the team's deliverable is made available. These dependent teams can then incorporate subsequent updates as necessary and when available. All teams must offer up a stable first version of their subsystems or components that collectively would constitute the project's baseline. |
|
|
|
|
|
|
|
|
New Term: A reasonably stable version of the application in development upon which each subsystem or component development team can build is a baseline. |
|
|
|
|
|
|
|
|
Tip
For more in-depth treatment of parallel development strategies, browse to an article by noted object technologist/OMT creator Jim Rumbaugh at http://www.rational.com/support/techpapers/omt/joop9509.html. |
|
|
|
|
|
|
|
|
|
Microsoft's Visual SourceSafe, which ships with the Professional and Enterprise Editions of Visual Basic, is a version control software system that can support serial and parallel development strategies. Some Visual Basic projects you've been on probably only implemented a serial development strategy, where your deliverable was absolutely dependent on that of another team. Thus, you probably had only one SourceSafe server, with everyone having full access to everyone else's subprojects. Setting up a parallel development strategy requires a little more effort, but is not difficult. You'll explore that strategy in the next section. |
|
|
|
|
|
|
|
|
If you have your Visual Basic CD-ROM and have not installed SourceSafe, do so now. Follow the instructions. Install both the administrative server and client units. Once you've completed the installation, log in to the server and set yourself up as a user using your name. |
|
|
|
|
|